Handling exceptions reported by media device meters

ABSTRACT

Apparatus, systems, articles of manufacture, and methods are disclosed for handling exceptions reported by media device meters. An example apparatus includes a static display detector to determine whether current measurements for a media presentation device at a time corresponding to an exception reported by a media device meter indicate the media presentation device was in a static display state at the time corresponding to the exception. The example apparatus includes a muted viewing detector to determine whether the media presentation device was in a muted viewing state at the time of the exception based on an audio level associated with the media presentation device, and an exception modifier to determine whether to modify the exception based on whether the media presentation device was in the static display state and whether the media presentation device was in a muted viewing state at the time of the exception.

RELATED APPLICATION

This patent arises from a continuation of U.S. patent application Ser.No. 16/121,898, which is titled “HANDLING EXCEPTIONS REPORTED BY MEDIADEVICE METERS,” and which was filed on Sep. 5, 2018. U.S. patentapplication Ser. No. 16/121,898 is incorporated herein by reference inits entirety. Priority to U.S. patent application Ser. No. 16/121,898 ishereby claimed.

FIELD OF THE DISCLOSURE

This disclosure relates generally to media device meters, and, moreparticularly, to apparatus, systems, articles of manufacture, andmethods for handling exceptions reported by media device meters.

BACKGROUND

Media device meters enable monitoring of media consumption. Media devicemeters can report exceptions to the monitoring of the media when themedia device meters are unable to identify media. Causes of someexceptions include malfunctioning of the media device meter or a lack ofperceptible media being presented around the media device meter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example environment and system for handling exceptionsreported by media devices meters that includes an example meterexception handler in accordance with the teachings of this disclosure.

FIG. 2 is a block diagram of the example meter exception handler of FIG.1 constructed in accordance with the teachings of this disclosure.

FIG. 3 is a flowchart representative of machine readable instructionswhich may be executed to implement the example meter exception handlerof FIGS. 1 and 2 .

FIGS. 4A-4B are example plots of meter exceptions and current data thatcan be analyzed by the meter exception handler of FIGS. 1 and 2 tohandle meter exceptions.

FIGS. 5A-5B are example plots of meter exceptions, current data, andvolume data that can be analyzed by the meter exception handler of FIGS.1 and 2 to handle meter exceptions.

FIG. 6 is a block diagram of an example processing platform structuredto execute the instructions of FIG. 3 to implement the example meterexception handler of FIGS. 1 and 2 .

The figures are not to scale. In general, the same reference numberswill be used throughout the drawing(s) and accompanying writtendescription to refer to the same or like parts.

DETAILED DESCRIPTION

Audience measurement entities (AMEs) desire knowledge on how usersinteract with media devices such as, for example, smartphones, tablets,laptops, televisions, smart televisions, radios, digital videorecorders, digital media players, etc. In particular, AMEs want tomonitor media presentations made at the media devices to, among otherthings, determine ownership and/or usage statistics of media devices,relative rankings of usage and/or ownership of media devices, types ofuses of media devices (e.g., whether a device is used for browsing theInternet, streaming media from the Internet, etc.), other types of mediadevice information, and/or other monitoring information including, forexample, advertisements exposure, advertisement effectiveness, userbehavior, purchasing behavior associated with various demographics, etc.

As used herein, the term “media” includes any type of content and/oradvertisement delivered via any type of distribution medium. Thus, mediaincludes television programming or advertisements, radio programming oradvertisements, movies, web sites, streaming media, etc. In examplesdisclosed herein, monitoring information includes, but is not limitedto, media identifying information (e.g., media-identifying metadata,codes, signatures, watermarks, and/or other information that may be usedto identify presented media), application usage information (e.g., anidentifier of an application, a time and/or duration of use of theapplication, a rating of the application, etc.), and/or user-identifyinginformation (e.g., demographic information, a user identifier, apanelist identifier, a username, etc.).

In some examples, to effectively monitor media consumption, AMEs employpanelists. These panelists are provided with monitoring devices,monitoring software, surveys, and/or other mechanisms to gather mediamonitoring information. For example, the panelists can be provided witha media device meter that includes data collection components, such as amicrophone, a wireless connection, input ports to connect topresentation devices, etc. Some media monitors are portable and can becarried around by the panelist (e.g., on their belt, in their pocket,etc.). Some media device meters are associated with specific mediapresentation devices (e.g., a television, a set top box, etc.) orspecific locations (e.g., a living room, a kitchen, etc.). In someexamples, the media device meter may require installation at apanelist's household. For example, the media device meter may beutilized to monitor usage of a television and consumption of media usingthe television. Such a media device meter can be installed by makingvideo, audio, and/or other data connections between the media devicemeter and the television.

When a media device meter is installed at a panelist's household toenable monitoring of a media presentation device, the media device metermay initially encounter exceptions due to an improperconfiguration/installation. For example, a media device meter canencounter exceptions pertaining to unviewable conditions, sometimesreferred to as excessive un-viewable (EUV) exceptions. If a media devicemeter encounters numerous times where the media presentation device isturned on (and monitoring is thus enabled on the media device meter) butthe media presentation device does not appear to be presenting anything,the media device meter can record an unviewable condition. Numerousoccurrences of an unviewable condition within a short time period canresult in an excessive un-viewable (EUV) exception. A media device metercan also encounter exceptions indicating “other” tuning, indicating thatthe media presentation device that is being monitored is powered on, buttuning data is not recognized. These types of exceptions are sometimesreferred to as “All-Other Tuning” exceptions. When a media device meterencounters an exception, the media device meter transmits the exception(along with other meter data) to the AME.

When a newly-installed media device meter is transmitting numerousexceptions to the AME, the AME may determine whether or not to send atechnician to the panelist's household to troubleshoot the exceptionsbeing issued by the media device meter. In some examples, the mediadevice meter is not actually misconfigured or improperly installed(e.g., resulting in incorrect exceptions), but rather is reportingexceptions that are correct. The correct exceptions are caused by themedia presentation device (which the media device meter is monitoring)being powered on, but operating in a muted viewing state and/or a staticdisplay state (e.g., a television is turned on, but a set top boxconnected to the television is turned off). In these examples, thetechnician is unnecessarily sent to the household to troubleshoot themedia device meter when the media device meter is actually functioningproperly and there is no configuration or installation issue.

Example apparatus, systems, articles of manufacture (e.g., physicalstorage media), and methods for handling exceptions reported by mediadevice meters are disclosed herein. Some example exception handlingtechniques disclosed herein include determining whether a mediapresentation device being monitored by the media device meter was in astatic display state at a time of the exception. In some examples,current measurements associated with the media presentation device atthe time of the exception are analyzed to determine (1) whether thecurrent draw at the time of the exception falls within a threshold rangeand/or (2) whether the current draw was constant within a thresholddeviation for a duration threshold. As used herein, the term “current,”refers to electrical current (e.g., AC current, DC current, etc.). Insome examples, in response to determining that the media device was notdisplaying a static display at the time of the exception, audiomeasurements can be utilized to determine whether the media presentationdevice was instead in a muted viewing state (e.g., corresponding to thetelevision presenting video content but no audio being presented) basedon an audio level at the time of the exception.

Example apparatus, systems, and articles of manufacture (e.g., physicalstorage media), and methods disclosed herein enable modification ofexceptions by flagging of metering exceptions as correct and/orincorrect based on whether the media presentation device was in thestatic display state, the muted viewing state, or neither of thesestates. For example, if it is determined that the media presentationdevice was in the static display state at the time of the exception, theexception can be flagged as “correct,” indicating that the meter isworking properly and encountered an exception due to the mediapresentation device not presenting perceptible media. Similarly, if itis determined that the media presentation device was in the mutedviewing state, the exception can be flagged as “correct.” In someexamples, in response to determining that the media presentation devicethat is being monitored by the media device meter is neither in thestatic display state nor the muted viewing state, the meter exception isflagged as being incorrect. An incorrect meter exception indicates thatthe exception did not occur due to the state of an audio or videopresentation on the media device. The incorrect meter exception could beindicative of a configuration and/or installation issue with the mediadevice meter. Thus, a media device meter correctly reports an exceptionwhen the media device meter reports that media is not being presentedbecause the media presentation device is in a static display state or amuted state. It is expected to have a correct exception reported.Whereas, the media meter device incorrectly reports an exception whenthere is no evidence that the media presentation device was in thestatic display state or muted state. In this example, it is unexpectedto have an exception reported and, therefore, the exception is anincorrect exception.

In determining whether the exception is correct or incorrect based onaudio data, current data, and/or other data associated with the mediapresentation device, the AME can remotely identify whether a meter isreporting exceptions due to a lack of perceptible media (a correctexception) or due to a possible issue with the media device meter (anincorrect exception). The examples disclosed herein can thereforesignificantly reduce the costs, time, and resources spent sendingtechnicians to troubleshoot media device meters at households byidentifying exceptions that are correct, and not indicative of technicalproblems with the media device meter. Further, these examples can beused to process media device meter exceptions at the AME and, therefore,flag exceptions as corresponding to media presentation devices in astatic display state, media presentation devices in a muted viewingstate, or neither of these states. This improvement in the granularityof the exception data can help AMEs analyze patterns in exceptions thatare reported and more accurately troubleshoot actual media device meterproblems.

FIG. 1 is an example environment 100 for handling exceptions reported bymedia devices meters in accordance with the teachings of thisdisclosure. The example environment 100 represents portions of anexample media monitoring system. The example environment 100 includes anexample first household 102 a, an example second household 102 b, anexample third household 102 c, an example first media presentationdevice 104 a, an example second media presentation device 104 b, anexample third media presentation device 104 c, an example first set topbox 106 a, an example second set top box 106 b, an example third set topbox 106 c, an example first outlet 108 a, an example second outlet 108b, an example third outlet 108 c, an example first media device meter110 a, an example second media device meter 110 b, an example thirdmedia device meter 100 c, an example first current sensor 112 a, anexample second current sensor 112 b, an example third current sensor 112c, an example audience measurement entity (AME) 114, and an examplemeter exception handler 116.

The example first, second, and third households 102 a, 102 b, 102 c ofthe illustrated example of FIG. 1 are locations where media monitoringis performed. For example, the first, second, and third households 102a, 102 b, 102 c can be panelist households. The example AME 114 canreceive data from any number of households. The first, second, and thirdhouseholds 102 a, 102 b, 102 c represent three possible meteringconfigurations to monitor the respective first, second, and third mediapresentation devices 104 a, 104 b, 104 c within the households.

The example first, second, and third media presentation devices 104 a,104 b, 104 c of the illustrated example of FIG. 1 present media withinthe respective first, second, and third households 102 a, 102 b, 102 c.In the illustrated example of FIG. 1 , the first, second, and thirdmedia presentation devices 104 a, 104 b, 104 c are televisions. However,the first, second, and third media presentation devices 104 a, 104 b,104 c could be any devices that present media. In some examples, thefirst, second, and third media presentation devices 104 a, 104 b, 104 care capable of directly presenting media (e.g., via a display), while insome examples, the first, second, and third media presentation devices130 present the media on separate equipment (e.g., via separatespeakers, via a video display, etc.). Any types or numbers of mediapresentation device(s) may be present in the first, second, and thirdhouseholds 102 a, 102 b, 102 c, and any combination of the mediapresentation device(s) in the first, second, and third households 102 a,102 b, 102 c can be monitored. For example, the media presentationdevices 104 a, 104 b, 104 c can be laptops, desktop computers, videogame counsels, tablet devices, digital media players, smart televisions,servers, etc.

The example first, second, and third set top boxes 106 a, 106 b, 106 cof the illustrated example of FIG. 1 provide media for presentation onthe first, second, and third media presentation devices 104 a, 104 b,104 c. For example, the first, second, and third set top boxes 106 a,106 b, 106 c can receive cable television signals and transmit the cabletelevision signals to the first, second, and third media presentationdevices 104 a, 104 b, 104 c. In some examples, the first, second, andthird media presentation devices 104 a, 104 b, 104 can be turned on, butwill not display media unless the respective first, second, and thirdset top boxes 106 a, 106 b, 106 c are turned on and tuned to a channel.In some examples, the first, second, and third media presentationdevices 104 a, 104 b, 104 c may not require the respective first,second, and third set top boxes 106 a, 106 b, 106 c, and mayadditionally or alternatively receive media directly at the presentationdevice (e.g., via a cable connection directly to the media presentationdevice, via a wireless signal, via an accessory attached to the mediapresentation device, via removable media such as a digital video disc,etc.).

The example first, second, and third outlets 108 a, 108 b, 108 c of theillustrated example of FIG. 1 serve as connections to power sources toprovide power for the first, second, and third media presentationdevices 104 a, 104 b, 104 c and/or the first, second, and third set topboxes 106 a, 106 b, 106 c. In some examples, the first, second, andthird outlets 108 a, 108 b, 108 c can be any type and/or number ofoutlets. For example, the first outlet 108 a can actually be twoseparate outlets, wherein the first media presentation device 104 a isplugged into (e.g., connected to) a first of the two separate outlets,and the first set top box 106 a is plugged into the second of the twoseparate outlets. In the illustrated example of FIG. 1 , the first andsecond current sensors 112 a, 112 b are also connected to the respectivefirst and second outlets 108 a, 108 b to enable current measurementsassociated with the respective first and second media presentationdevices 104 a, 104 b.

The example first, second, and third media device meters 110 a, 110 b,110 c of the illustrated example of FIG. 1 collect data pertaining tomedia consumption in the respective first, second, and third households102 a, 102 b, 102 c. In some examples, the first, second, and thirdmedia device meters 110 a, 110 b, 110 c include microphones, directconnections (e.g., data connections) to the respective first, second,and third media presentation devices 104 a, 104 b, 104 c, wirelessconnections to the respective first, second, and third mediapresentation devices 104 a, 104 b, 104 c, cameras, and/or any othercomponents to enable media monitoring. The example first, second, andthird media device meters 110 a, 110 b, 110 c transmit meter data to theAME 114, where the meter data can be processed by the meter exceptionhandler 116. In some examples, the first, second, and third media devicemeters 110 a, 110 b, 110 c are connected to the first, second, and thirdmedia presentation devices 104 a, 104 b, 104 c and/or to the first,second, and third set top boxes 106 a, 106 b, 106 c. In the examplesecond and third households 102 b, 102 c the example second and thirdmedia device meters 110 b, 110 c include the example second and thirdcurrent sensors 112 b, 112 c. For example, the example second and thirdcurrent sensors 112 b, 112 c may be housed within or otherwise integralwith the example second the third media device meters 110 b, 100 c,respectively.

The example first, second, and third current sensors 112 a, 112 b, 112 cof the illustrated example of FIG. 1 determine current measurementsassociated with the respective first, second, and third mediapresentation devices 104 a, 104 b, 104 c. The first current sensor 112 aof the first household 102 a is separate from the first media devicemeter 110 a and is connected to the first outlet 108 a. In someexamples, the first current sensor 112 a is an attachment to the firstoutlet that measures the current associated with any other deviceconnected to the first outlet 108 a. The example second current sensor112 b is connected to the second outlet 108 b, but, unlike the firstcurrent sensor 112 a, the second current sensor 112 b is part of (e.g.,included within) the second media meter device 110 b. In such anexample, the second media meter device 110 b can be connected to thesecond outlet 108 b, to enable the second current sensor 112 b tocollect current measurements associated with the second mediapresentation device 104 b. The example third current sensor 112 c ispart of the third media meter device 110 c. However, instead of beingconnected directly to the third outlet 108 c, the third current sensor112 c is connected to the third media presentation device 104 c. In thisconfiguration, the third current sensor 112 c is connected to circuitryof the third media presentation device 104 c to determine currentmeasurements of the third media presentation device 104 c. While theexample configurations of the first, second, and third current sensors112 a, 112 b, 112 c represent three possible configurations to collectcurrent measurements from respective first, second, and third mediapresentation devices 104 a, 104 b, 104 c, the first, second, and thirdcurrent sensors 112 a, 112 b, 112 c could be any devices and/or softwareto determine current measurements of media presentation devices. In someexamples, the first, second, and third current sensors 112 a, 112 b, 112c transmit current data to the AME 114. In some examples, the first,second, and third current sensors 112 a, 112 b, 112 c transmit currentdata to the meter exception handler 116.

The example AME 114 of the illustrated example of FIG. 1 is an entityresponsible for collecting media monitoring information. The example AME114 collects current data and meter data from the first, second, andthird households 102 a, 102 b, 102 c. In some examples, the AME 114 isassociated with one or more locations (e.g., a central facility) wheredata is aggregated and/or analyzed. The example AME 114 includes themeter exception handler 116 to assess meter exceptions and determinewhether the meter exceptions are correct or incorrect. In response tothe meter exception handler 116 determining that one or more meterexceptions issued by one of the first, second, and/or third media devicemeters 110 a, 110 b, 110 c are incorrect (e.g., due to possiblemalfunction of the respective media device meter), the AME 114 canperform troubleshooting tasks to correct problems associated with therespective meter(s) (e.g., perform remote troubleshooting, send atechnician to the household, etc.).

The example meter exception handler 116 of the illustrated example ofFIG. 1 analyzes exceptions from the first, second, and third mediadevice meters 110 a, 110 b, 110 c. In some examples, the meter exceptionhandler 116 accesses meter data, including meter exceptions and audiodata, from one or more of the first, second, and/or third media devicemeters 110 a, 110 b, 110 c, as well as current data from one or more ofthe first, second, and/or third current sensors 112 a, 112 b, 112 c. Insome examples, when a meter exception is accessed by the meter exceptionhandler 116, the meter exception handler 116 accesses current data andaudio data for the media presentation device 104 a, 104 b, 104 cassociated with the exception. In such examples, the current data andaudio data corresponding to the time of the exception is analyzed.

The meter exception handler 116 can determine whether the mediapresentation device 104 a, 104 b, 104 c to which the meter data andcurrent data corresponds was in a static display state at the time ofthe exception, or whether the media presentation device 104 a, 104 b,104 c was in a muted viewing state at the time of the exception. In someexamples, to determine whether the media presentation device 104 a, 104b, 104 c was in the static display state, the meter exception handler116 determines whether the current data falls within a threshold rangeat the time of the exception, and/or whether the current remainedconstant within a deviation threshold for a duration threshold. In someexamples, to determine whether the media presentation device 104 a, 104b, 104 c was in a muted viewing state at the time of the exception, themeter exception handler 116 additionally or alternatively determineswhether an audio level at the time of the exception was below a volumethreshold.

In response to determining that the media presentation device 104 a, 104b, 104 c was in either the static display state or the muted viewingstate at the time of an exception, the meter exception handler 116 flagsthe exception as correct (e.g., because the media device meter 110 a,110 b, 110 c is operating correctly in reporting an exception, as thereis no perceptible media being presented). Conversely, in response todetermining that the media presentation device 104 a, 104 b, 104 c wasnot in the static display state nor the muted viewing state at the timeof the exception, the meter exception handler 116 flags the exception asincorrect. In some examples, the meter exception handler 116 reportsmeter exceptions that are incorrect to the AME 114 to enable the AME 114to initiate corrective action on the media device meter 110 a, 110 b,110 c associated with the incorrect meter exception.

In operation, the first, second, and third households 102 a, 102 b, 102c include respective first, second, and third media presentation devices104 a, 104 b, 104 c that access media using respective first, second,and third set top boxes 106 a, 106 b, 106 c. The first, second, andthird media presentation devices 104 a, 104 b, 104 c and the first,second, and third set top boxes 106 a, 106 b, 106 c obtain power via therespective first, second, and third outlets 108 a, 108 b, 108 c. Thefirst, second, and third media device meters 110 a, 110 b, 110 c monitormedia presented by the respective first, second, and third mediapresentation devices 104 a, 104 b, 104 c, while the first, second, andthird current sensors 112 a, 112 b, 112 c determine current measurementsassociated with the first, second, and third media presentation devices104 a, 104 b, 104 c. The current data collected by the first, second,and third current sensors 112 a, 112 b, 112 c and the meter datacollected by the first, second, and third media device meters 110 a, 110b, 110 c are transmitted to the AME 114, where the current data and themeter data are received by the meter exception handler 116 forprocessing to identify correct and incorrect meter exceptions. The meterexception handler 116 generates meter exception assessment data based onthe analysis of the current data and the meter data.

FIG. 2 is a block diagram of the example meter exception handler 116 ofFIG. 1 constructed in accordance with the teachings of this disclosure.The example meter exception handler 116 includes an example currentmeasurement receiver 202, an example static display detector 204, anexample audio level detector 206, an example muted viewing detector 208,an example exception data receiver 210, an example exception modifier212, and an example data store 214.

The example current measurement receiver 202 of the illustrated exampleof FIG. 2 accesses and/or receives current data. In some examples, thecurrent measurement receiver 202 accesses current data corresponding toa specific current sensor (e.g., the first current sensor 112 a)associated with a specific media device meter (e.g., the first mediadevice meter 110 a). In some examples, the current measurement receiver202 only accesses a subset of the current data corresponding to a timeof an exception (e.g., thirty seconds prior to the exception, thirtyseconds after the exception, etc.). The current measurement receiver 202can request the current data in response to the exception data receiver210 accessing and/or receiving an exception or data indicative of anexception. In some examples, the current measurement receiver 202accesses current data as the current data is transmitted from currentsensors and/or media device meters. The current measurement receiver 202can access current data and communicate the current data to the staticdisplay detector 204.

The example static display detector 204 of the illustrated example ofFIG. 2 determines whether a media presentation device was in a staticdisplay state at a time of an exception. In some examples, the staticdisplay detector 204 receives current data for a time associated with anexception from the current measurement receiver 202. In some examples,the static display detector 204 requests current measurement data fromthe current measurement receiver 202 in response to the exception datareceiver 210 identifying an exception and indicating a time associatedwith the exception to the static display detector 204. The staticdisplay detector 204 compares current measurements at the time of theexception with a threshold range associated with a static display. Forexample, if a television operates between 200 milliamperes (mA) and 250mA when displaying a static screen, the static display detector 204 cancompare current measurements at the time of the exception with thisthreshold range (e.g., 200 mA to 250 mA).

In some examples, the static display detector 204 also compares currentmeasurements at the time of the exception with a deviation threshold todetermine whether the current measurements deviate more than a staticdisplay would. For example, the static display detector 204 determines adeviation value associated with the current measurements for a durationthreshold (e.g., five seconds surrounding the exception, two secondssurrounding the exception, etc.) and determines whether the currentdeviation meets or exceeds the threshold deviation to identify a staticdisplay state. In some examples, in response to (1) the currentmeasurements at the time of the exception falling within the thresholdrange and (2) the current measurements having a deviation less than athreshold deviation for a duration threshold (e.g., a time surroundingthe exception), the static display detector 204 can determine that themedia presentation device associated with the exception was in a staticdisplay state at the time of the exception.

In some examples, after processing current data associated with anexception, the static display detector 204 informs the exceptionmodifier 212 of whether the media presentation device associated withthe exception was in a static display state at the time of theexception, thereby enabling the exception modifier 212 to determinewhether the exception was correct or incorrect. In addition, in someexamples, in response to determining the media presentation deviceassociated with the exception was not in a static display state, thestatic display detector 204 informs the muted viewing detector 208 todetermine whether the media presentation device was in a muted viewingstate.

The example audio level detector 206 of the illustrated example of FIG.2 accesses and/or receives audio data included in meter data from mediadevice meters. For example, the audio level detector 206 can accessaudio data conveyed in the meter data from the first, second, and thirdmedia device meters 110 a, 110 b, 110 c. In some examples, the audiodata is transmitted to the meter exception handler 116 separately fromthe meter exception data. The audio level detector 206 determines volumelevels associated with audio data. For example, the audio level detector206 can sample audio data and store volume levels associated with thesamples of the audio data, along with storing the times associated withthe samples. Subsequently, the muted viewing detector 208 can utilizethese volume levels to determine whether a media presentation deviceassociated with an exception was in a muted viewing state at a time ofthe exception.

In some examples, the audio level detector 206 only determines volumelevels associated with audio data captured at a time associated with anexception accessed by the exception data receiver 210. In other words,in some examples, the audio level detector 206 is triggered to operatewhen an exception has been identified. In some examples, the audio leveldetector 206 transmits audio data specific to a time associated with anexception to the muted viewing detector 208 in response to the exceptiondata receiver 210 accessing an exception.

The example muted viewing detector 208 of the illustrated example ofFIG. 2 determines whether a media presentation device was in a mutedviewing state at a time of an exception. In some examples, to determinethat the media presentation device was in the muted viewing state, themuted viewing detector 208 determines (1) that the media presentationdevice was not in a static display state at the time of the exception,and (2) that the audio data indicates the audio was below a volumethreshold at the time of the exception. For example, the muted viewingdetector 208 can access information from the static display detector 204indicating whether or not an exception was associated with a staticdisplay state. Further, the muted viewing detector 208 can compare audiodata at the time of the exception from the audio level detector 206 witha volume threshold. In some examples, when the muted viewing detector208 determines that an exception is associated with a muted viewingstate, the muted viewing detector 208 transmits an indication to theexception modifier 212 that the media presentation device associatedwith the exception was in a muted viewing state at the time of theexception.

The example exception data receiver 210 of the illustrated example ofFIG. 2 accesses meter exception data from the media device meters 110 a,110 b, 110 c. In some examples, the exception data receiver 210 receivesexceptions as the exceptions are encountered at the media devicemeter(s) 110 a, 110 b, 110 c and transmitted to the exception datareceiver 210 for processing. In some examples, the exception datareceiver 210 receives exceptions from the media device meters 110 a, 110b, 110 c in batches (e.g., the media device meters 110 a, 110 b, 110 ctransmit exceptions to the exception data receiver 210 at regularintervals, the media device meters 110 a, 110 b, 110 c transmitexceptions to the exception data receiver 210 when a threshold number ofexceptions have been encountered, etc.). In some examples, the exceptiondata receiver 210 communicates with the current measurement receiver202, the static display detector 204, the audio level detector 206,and/or the muted viewing detector 208 to initiate analysis of currentmeasurements and/or audio level data associated with a time of areceived exception. The example exception data receiver 210 communicatesexceptions and/or data associated with exceptions (e.g., times of theexceptions, exception types, etc.) to the exception modifier 212.

The example exception modifier 212 of the illustrated example of FIG. 2analyzes exceptions and determines whether the exceptions are correct orincorrect. In some examples, when the exception modifier 212 accesses anexception, the exception modifier 212 can request data from the staticdisplay detector 204 and/or the muted viewing detector 208 pertaining toa time associated with the exception. In some examples, the exceptionmodifier 212 designates (e.g., flags, labels) an exception as correct inresponse to the static display detector 204 indicating that a mediapresentation device associated with the exception was in a staticdisplay state at the time of the exception and/or in response to themuted viewing detector 208 indicating that the media presentation deviceassociated with the exception was in a muted viewing state at the timeof the exception. In response to determining that an exception iscorrect, the exception modifier 212 can indicate that the exception doesnot require troubleshooting (e.g., troubleshooting to correct an issuewith a media device meter) by the AME 114.

In some examples, in response to the exception modifier 212 determiningthat a media presentation device associated with an exception was not ina static display state and not in a muted viewing state at a timeassociated with the exception, the exception modifier 212 designates(e.g., flags, labels, etc.) the exception as incorrect. In response toidentifying an incorrect exception, the exception modifier 212 caninitiate a troubleshooting process at the AME 114 to determine and/oraddress a cause of the incorrect exception. In some examples, theexception modifier 212 outputs meter exception assessment dataindicating whether exceptions are correct or incorrect.

The example data store 214 is a storage location that can be used tostore current data, audio data, meter exception data, and/or meterexception assessment data. The data store 214 can be implemented by avolatile memory (e.g., a Synchronous Dynamic Random Access Memory(SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic RandomAccess Memory (RDRAM), etc.) and/or a non-volatile memory (e.g., flashmemory, etc.). The data store 214 can additionally or alternatively beimplemented by one or more double data rate (DDR) memories, such as DDR,DDR2, DDR3, mobile DDR (mDDR), etc. The data store 214 can additionallyor alternatively be implemented by one or more mass storage devices suchas hard disk drive(s), compact disk drive(s) digital versatile diskdrive(s), etc. While, in the illustrated example, the data store 214 isillustrated as a single database, the data store 214 can be implementedby any number and/or type(s) of databases. Furthermore, the data storedin the data store 214 can be in any data format such as, for example,binary data, comma delimited data, tab delimited data, structured querylanguage (SQL) structures, etc.

In operation, the example current measurement receiver 202 accessescurrent data and communicates the current data to the static displaydetector 204. The static display detector 204 determines whether a mediapresentation device was in a static display state at a time of anexception based on whether the current data is within a threshold rangeand/or is constant within a deviation threshold for a durationthreshold. The audio level detector 206 accesses audio data andcommunicates the audio data to the muted viewing detector 208 whichdetermines whether a media presentation device was in a muted viewingstate at a time of an exception. For example, the muted viewing detector208 can determine the media presentation device was in the muted viewingstate when the audio data indicates an audio level below a threshold.The example exception data receiver 210 accesses exceptions from mediadevice meters and communicates the exceptions to the exception modifier212. The exception modifier 212 designates the exceptions as beingcorrect or incorrect based on information from the static displaydetector 204 and/or the muted viewing detector 208. The exceptionmodifier 212 thereby generates meter exception assessment data, whichcan be stored, in addition or alternatively to the current data, audiodata, and meter exception data, in the data store 214.

While an example manner of implementing the meter exception handler 116of FIG. 1 is illustrated in FIG. 2 , one or more of the elements,processes and/or devices illustrated in FIG. 2 may be combined, divided,re-arranged, omitted, eliminated, and/or implemented in any other way.For example, in some examples, the media exception handler 116 may beincorporated into a media device meter 110 a, 110 b, 110 c where data islocally processed and results are transmitted to the AME 114. Further,the example media device meter 110 a, 110 b, 110 c, the example currentmeasurement receiver 202, the static display detector 204, the audiolevel detector 206, the example muted viewing detector 208, the exampleexception data receiver 210, the example exception modifier 212, theexample data store 214 and/or, more generally, the example meterexception handler 116 of FIG. 2 may be implemented by hardware,software, firmware and/or any combination of hardware, software, and/orfirmware. Thus, for example, any of the example media device meter 110a, 110 b, 110 c, the example current measurement receiver 202, thestatic display detector 204, the audio level detector 206, the examplemuted viewing detector 208, the example exception data receiver 210, theexample exception modifier 212, the example data store 214 and/or, moregenerally, the example meter exception handler 116 of FIG. 2 could beimplemented by one or more analog or digital circuit(s), logic circuits,programmable processor(s), programmable controller(s), graphicsprocessing unit(s) (GPU(s)), digital signal processor(s) (DSP(s)),application specific integrated circuit(s) (ASIC(s)), programmable logicdevice(s) (PLD(s)), and/or field programmable logic device(s) (FPLD(s)).When reading any of the apparatus or system claims of this patent tocover a purely software and/or firmware implementation, at least one ofthe example media device meter 110 a, 110 b, 110 c, the example currentmeasurement receiver 202, the static display detector 204, the audiolevel detector 206, the example muted viewing detector 208, the exampleexception data receiver 210, the example exception modifier 212, theexample data store 214 and/or, more generally, the example meterexception handler 116 of FIG. 2 is/are hereby expressly defined toinclude a non-transitory computer readable storage device or storagedisk such as a memory, a digital versatile disk (DVD), a compact disk(CD), a Blu-ray disk, etc. including the software and/or firmware.Further still, the example meter exception handler 116 of FIG. 2 mayinclude one or more elements, processes, and/or devices in addition to,or instead of, those illustrated in FIG. 2 , and/or may include morethan one of any or all of the illustrated elements, processes, anddevices. As used herein, the phrase “in communication,” includingvariations thereof, encompasses direct communication and/or indirectcommunication through one or more intermediary components, and does notrequire direct physical (e.g., wired) communication and/or constantcommunication, but rather additionally includes selective communicationat periodic intervals, scheduled intervals, aperiodic intervals, and/orone-time events.

A flowchart representative of example hardware logic, machine readableinstructions, hardware implemented state machines, and/or anycombination thereof for implementing the meter exception handler of FIG.2 is shown in FIG. 3 . The machine readable instructions may be anexecutable program or portion of an executable program for execution bya computer processor such as the processor 612 shown in the exampleprocessor platform 600 discussed below in connection with FIG. 6 . Theprogram may be embodied in software stored on a non-transitory computerreadable storage medium such as a CD-ROM, a floppy disk, a hard drive, aDVD, a Blu-ray disk, or a memory associated with the processor 612, butthe entire program and/or parts thereof could alternatively be executedby a device other than the processor 612 and/or embodied in firmware ordedicated hardware. Further, although the example program is describedwith reference to the flowchart illustrated in FIG. 3 , many othermethods of implementing the example meter exception handler 116 mayalternatively be used. For example, the order of execution of the blocksmay be changed, and/or some of the blocks described may be changed,eliminated, or combined. Additionally or alternatively, any or all ofthe blocks may be implemented by one or more hardware circuits (e.g.,discrete and/or integrated analog and/or digital circuitry, an FPGA, anASIC, a comparator, an operational-amplifier (op-amp), a logic circuit,etc.) structured to perform the corresponding operation withoutexecuting software or firmware.

As mentioned above, the example processes of FIG. 3 may be implementedusing executable instructions (e.g., computer and/or machine readableinstructions) stored on a non-transitory computer and/or machinereadable medium such as a hard disk drive, a flash memory, a read-onlymemory, a compact disk, a digital versatile disk, a cache, arandom-access memory, and/or any other storage device or storage disk inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, for brief instances, for temporarily buffering,and/or for caching of the information). As used herein, the termnon-transitory computer readable medium is expressly defined to includeany type of computer readable storage device and/or storage disk and toexclude propagating signals and to exclude transmission media.

“Including” and “comprising” (and all forms and tenses thereof) are usedherein to be open ended terms. Thus, whenever a claim employs any formof “include” or “comprise” (e.g., comprises, includes, comprising,including, having, etc.) as a preamble or within a claim recitation ofany kind, it is to be understood that additional elements, terms, etc.may be present without falling outside the scope of the correspondingclaim or recitation. As used herein, when the phrase “at least” is usedas the transition term in, for example, a preamble of a claim, it isopen-ended in the same manner as the term “comprising” and “including”are open ended. The term “and/or” when used, for example, in a form suchas A, B, and/or C refers to any combination or subset of A, B, C such as(1) A alone, (2) B alone, (3) C alone, (4) A with B, (5) A with C, (6) Bwith C, and (7) A with B and with C.

Example machine readable instructions 300 that may be executed by themeter exception handler 116 are illustrated in FIG. 3 . With referenceto the preceding figures and associated descriptions, the examplemachine readable instructions 300 of FIG. 3 begin with the example meterexception handler 116 accessing an exception reported in meter data(block 302). For example, the exception data receiver 210 can access anexception reported in meter data by a media device meter (e.g., thefirst, second, and third media device meters 110 a, 110 b, 110 c of FIG.1 ).

At block 304, the example meter exception handler 116 accesses currentmeasurement values associated with a timestamp of the exception. In someexamples, the current measurement receiver 202 accesses currentmeasurement values associated with a timestamp of the exception. In someexamples, the static display detector 204, in response to the exceptiondata receiver 210 accessing the exception, requests the currentmeasurement values associated with the timestamp of the exception fromthe current measurement receiver 202. In some examples, the staticdisplay detector 204 accesses current measurement values for the mediapresentation device corresponding to the exception for a time rangearound the timestamp of the exception (e.g., five seconds before thetimestamp and five seconds after the timestamp, ten seconds before thetimestamp and ten seconds after the timestamp, and/or other suitableranges).

At block 306, the example meter exception handler 116 accesses audiolevel data associated with the time stamp of the exception. In someexamples, the audio level detector 206 accesses audio level dataassociated with the time stamp of the exception. In some examples, theaudio level detector 206 continually accesses audio data from aplurality of media device meters (e.g., the first, second, and thirdmedia device meters 110 a, 110 b, 110 c), while in some examples, theaudio level detector 206 accesses audio data from media device meter(s)associated with exception(s) in response to the exception data receiver210 accessing the exception(s) corresponding to the respective mediadevice meter(s). In some examples, the audio level detector 206 accessesaudio level data for a time range around the timestamp of the exception(e.g., five seconds before the timestamp and five seconds after thetimestamp, ten seconds before the timestamp and ten seconds after thetimestamp, and/or other suitable ranges).

At block 308, the example meter exception handler 116 determines whetherthe current measurements at the time of the meter exception fall withina threshold range. In some examples, the static display detector 204compares current measurements associated with the media device meter atthe time of the exception with a threshold range (e.g., a lower limitcurrent value and an upper limit current value). For example, the staticdisplay detector 204 can determine whether current measurements for fiveseconds prior to the time of the timestamp and/or for five seconds afterthe time of the timestamp are within the threshold range. Example plotsdepicting current measurements being compared to an example thresholdrange are illustrated and described in connection with FIGS. 4A-4B. Inresponse to the current measurements at the time of the meter exceptionfalling within the threshold range, processing of the exampleinstructions 300 transfers to block 312. Conversely, in response tocurrent measurements at the time of the meter exception not fallingwithin the threshold range, processing of the example instructions 300transfers to block 314.

At block 310, the example meter exception handler 116 determines whethercurrent measurements were constant within a deviation threshold for aduration threshold. For example, the static display detector 204 candetermine whether, for a duration threshold (e.g., one second before andone second after the exception, five seconds before and five secondsafter the exception, and/or other suitable ranges), the currentmeasurements remained within a deviation threshold (e.g., a two percentdeviation from the current value at the time of the meter exception, a 5mA deviation from the current value at the time of the meter exception,and/or other suitable ranges of these and/or other suitable parameters).In some examples, the deviation threshold is measured relative to thecurrent value at the time of the exception. In some examples, thedeviation threshold is measured as a maximum change throughout theduration threshold (e.g., the minimum current value subtracted from themaximum current value from within the duration threshold). The deviationthreshold is intended to determine whether the screen is truly static(non-changing), as the current measurements may, in some examples,satisfy the threshold range (e.g., associated with block 308), butactually be fluctuating within that range due to different televisionconfigurations (e.g., which may be presenting media, but utilizing loweramperage settings). Example plots depicting current measurementdeviation values are illustrated and described in connection with FIGS.4A-4B. In response to the current measurements being constant within thedeviation threshold for the duration threshold, processing of theexample instructions 300 transfers to block 312. Conversely, in responseto determining that the current measurements were not constant withinthe deviation threshold for the duration threshold, processing of theexample instructions 300 transfers to block 314.

At block 312, the example meter exception handler 116 flags the meterexception as corresponding to a static display state. In some examples,the exception modifier 212 flags (e.g., labels, tags, designates, etc.)the meter exception as corresponding to the static display state.

At block 314, the example meter exception handler 116 determines whetherthe audio was below a volume threshold at the time of the meterexception. In some examples, the muted viewing detector 208 determineswhether the audio was below a volume threshold at the time of the meterexception. In some examples, the volume threshold is configured to beset at a level higher than would be generated by ambient noise (e.g.,heating, ventilation, and air conditioning (HVAC) noises, personswalking around, quiet speaking, etc.) but lower than would be generatedby quiet media on the media presentation device. In some examples, ifthe audio data is collected directly from the media presentation deviceas opposed to recorded via a microphone, the volume threshold can beconfigured to be very low, as a muted program should have no volumeoutput. In response to determining that the audio was below a volumethreshold at the time of the meter exception, processing of the exampleinstructions 300 transfers to block 316. Conversely, in response todetermining that the audio was not below the volume threshold at thetime of the meter exception, processing of the example instructions 300transfers to block 320.

At block 316, the example meter exception handler 116 flags the meterexception as corresponding to a muted viewing state. In some examples,the exception modifier 212 flags (e.g., labels, tags, designates, etc.)the meter exception as corresponding to the muted viewing state.

At block 318, the example meter exception handler 116 flags the meterexception as correct. In some examples, the exception modifier 212 flagsthe meter exception as correct, thereby generating meter exceptionassessment data. In addition, at block 320, the example meter exceptionhandler 116 flags the meter exception as incorrect. In some examples,the exception modifier 212 flags the meter exception as correct, therebygenerating meter exception assessment data. In some examples, the meterexception handler 116 can choose to not flag either correct exceptions,or incorrect exceptions, and only flag one type (e.g., only flag“incorrect” exceptions), implying that all non-flagged exceptions arethe opposite. For example, if the meter exception handler 116 only flagsincorrect exceptions, any meter exception that is not flagged can beconsidered correct.

At block 322, the example meter exception handler 116 determines whetherthere are any additional meter exceptions to process. In some examples,the exception data receiver 210 determines whether there are anyadditional meter exceptions to process. In response to there beingadditional meter exceptions to process, processing of the exampleinstructions 300 transfers to block 302. Conversely, in response tothere not being additional meter exceptions to process, processingterminates.

FIGS. 4A-4B are plots of meter exceptions and current data that can beanalyzed by the meter exception handler 116 to handle meter exceptions.FIG. 4A includes an example meter exception plot 400, and an examplefirst current plot 406. The example meter exception plot 400 includes anexample meter exception 402 corresponding to an example meter exceptiontime 404. The example first current plot 406 includes an exampleduration threshold 408 (ΔT), an example duration threshold end time 410,an example lower current threshold 412 (A_(LOW)), an example uppercurrent threshold 414 (A_(HIGH)), an example first minimum current value416, an example first maximum current value 418, and an example firstcurrent deviation 420 (ΔA).

The example meter exception plot 400 includes a time axis extending tothe right from a zero time value, and a discrete meter exceptions line,where meter exceptions that are encountered are indicated by “X”symbols. The example meter exception 402 corresponds to a meterexception recorded at a media device meter (e.g., one of the first,second, and third media device meters 110 a, 110 b, 110 c). The meterexception 402 is stored and/or transmitted to the meter exceptionhandler 116 with the meter exception time 404, which designates the timeat which the meter exception 402 occurred. The meter exception plot 400includes a plurality of exceptions that occur in succession with thefirst meter exception 402. For brevity, the meter exception 402 is theonly meter exception that is analyzed and discussed, but the sameanalysis can be performed on other ones of the plurality of meterexceptions.

The example first current plot 406 includes a time axis as the x-axisextending to the right from a zero time value, and a current axis as they-axis representing current values in amperes, extending upward from azero ampere value. When analyzing current measurements to determine if amedia presentation device was in a static display state, the meterexception handler 116 can analyze a duration threshold beginning at themeter exception time 404 and extending to the duration threshold endtime 410. The duration threshold 408 could be any time value extendingprior to the meter exception time 404 and/or after the meter exceptiontime 404. For simplicity, for the current plots displayed in FIGS. 4A-4Band FIGS. 5A-5B, the duration threshold is represented as a brief timeperiod beginning at the meter exception time 404 and extending forseveral seconds (e.g., until the duration threshold end time 410).

As described in block 308 of the flowchart of FIG. 3 , the meterexception handler 116 determines whether current measurements associatedwith a meter exception fall within a threshold range. The first currentplot 406 includes the lower current threshold 412 and the upper currentthreshold 414. These thresholds represent a range of current values thata media presentation device having a static display would be predictedto exhibit. For example, some media presentation devices may present astatic display with a relatively higher current value relative to othermedia presentation devices. Similarly, some types of static displays(e.g., different colors, patterns, etc.) may correspond to highercurrent values than other types of displays. The meter exception handler116 determines whether current measurements during the durationthreshold 408 fall within the threshold range (e.g., are higher than thelower current threshold 412, and lower than the upper current threshold414). In the first current plot 406, the values are within this rangeduring the time period of the duration threshold 408. In some examples,the meter exception handler 116 analyzes a current value at the meterexception time 404 to determine whether the current value falls withinthe threshold range, without analyzing current measurements for the fullduration threshold 408.

As described in block 312 of the flowchart of FIG. 3 , the meterexception handler 116 determines whether current measurements wereconstant within a deviation threshold for a duration threshold. Thefirst current plot 406 includes the first minimum current value 416 andthe first maximum current value 418, representing respective minimum andmaximum current values observed during the duration threshold 408. Thedifference between the first maximum current value 418 and the firstminimum current value 416 is represented as the first current deviation420. In some examples, the current deviation can be represented as apercent change from a current value at the meter exception time 404, asa standard deviation value, or any other means of quantifying the amountof variance in the current measurements during the duration threshold408. The example first current deviation 420 can be compared to adeviation threshold to determine whether the media presentation deviceassociated with an exception was in a static display state at the timeof the exception. As the first current deviation 420 is relativelysmall, and the current measurements are relatively constant during theduration threshold 408, the meter exception handler 116 may determinethat the current deviation 420 is less than the deviation threshold andthat the media presentation device was in a static display state at thetime of the exception 402. If the meter exception handler 116 determinedthat the media presentation device was in the static display state, themeter exception 402 is labeled as correct (e.g., the media device meterassociated with the exception encountered the exception because themedia presentation device was not presenting perceptible media).

FIG. 4B includes the meter exception plot 400, with a second currentplot 422, representing different possible current measurements. Thesecond current plot 422 includes the lower current threshold 412(A_(LOW)) and the upper current threshold 414 (A_(HIGH)). As in FIG. 4B,the current measurements during the duration threshold 408 (ΔT) fallwithin the threshold range (e.g., are above the lower current threshold412 but below the upper current threshold 414). However, the currentmeasurements during the duration threshold 408 include an example secondmaximum current value 424, representing the maximum current valueobserved during the duration threshold 408, and an example secondminimum current value 426, representing the minimum current valueobserved during the duration threshold 408. An example second currentdeviation 428 (ΔA′) represents the difference between the second maximumcurrent value 424 and the second minimum current value 426. The secondcurrent deviation 428 is larger than the first current deviation 420. Insome examples, when the meter exception handler 116 compares the secondcurrent deviation to the deviation threshold, the meter exception 402associated with the second current plot 422 may not satisfy thedeviation threshold for the duration threshold 408, thus resulting inthe meter exception handler 116 determining that the media presentationdevice associated with the meter exception 402 was not in a staticdisplay state at the time of the meter exception 402. The example secondcurrent plot 422 may be associated with a media presentation device thatoperates at lower current values, as the current measurements throughoutthe plot remain mostly within the threshold range, but have highdeviation, which is not characteristic of a static display state.

FIGS. 5A-5B are plots of meter exceptions, current data, and volume datathat can be analyzed by the meter exception handler 116 to handle meterexceptions. FIG. 5A includes the meter exception plot 400, as well as anexample third current plot 502, and an example first volume plot 504.While FIG. 4A includes the same meter exception plot 400, the examplethird current plot 502 and the first volume plot 504 represent differentpossible analysis outcomes corresponding to different current data andutilizing volume data to determine whether a media presentation devicewas in a muted viewing state.

The example third current plot 502 depicts current measurement datacorresponding to times around the meter exception time 404. The thirdcurrent plot 502 includes the lower current threshold 412 (A_(LOW)) andthe upper current threshold 414 (A_(HIGH)). The current measurementsduring the duration threshold 408 (ΔT) exceed the upper currentthreshold 414. As a result, based on this example data, the meterexception handler 116 determines that the media presentation deviceassociated with the meter exception 402 was not in a static displaystate at the meter exception time 404.

The example first volume plot 504 depicts volume data around the meterexception time 404. The first volume plot 504 includes an example firstvolume level 506 associated with the volume measurement at the meterexception time 404. The first volume plot 504 also includes an examplevolume threshold 508 (VOL_(MAX)) representing a maximum volume levelthat can be associated with a media presentation device in a mutedviewing state. In the first volume plot 504, the first volume level 506,associated with the meter exception time 404, is below the volumethreshold 508. In some examples, the meter exception handler 116determines the media presentation device associated with the exception402 is in a muted viewing state based on the first volume level 506being below the volume threshold 508 and based on the media presentationdevice not being in a static display state. In some examples, the meterexception handler 116 additionally or alternatively analyzes volumelevels throughout the duration threshold 408 to determine if the volumeremains below the volume threshold 508 for the entire duration threshold408. Based on the volume data associated with the first volume plot 504,the first volume level 506, as well as all volume levels in the durationthreshold 408, remain below the volume threshold 508. Therefore, basedon the third current plot 502 indicating that the media presentationdevice associated with the exception 402 is not in a static displaystate, and the volume levels remaining below the volume threshold 508,the meter exception handler 116 determines that the meter exception 402is associated with a muted viewing state.

FIG. 5B includes the meter exception plot 400, the third current plot502, and an example second volume plot 510. The volume data representedby the second volume plot 510 indicates another example meter exceptionanalysis outcome. The second volume plot 510 includes an example secondvolume level 512 that is above the volume threshold 508. Therefore, themeter exception handler 116, performing analysis on the data representedin FIG. 5B, may determine that the media presentation device associatedwith the meter exception 402 does not correspond to a muted viewingstate, based on the second volume level 512 being above the volumethreshold 508 and the current measurements being outside the thresholdrange associated with the lower current threshold 412 and the uppercurrent threshold 414.

FIG. 6 is a block diagram of an example processor platform 1000structured to execute the instructions of FIG. 3 to implement the meterexception handler 116 of FIGS. 1 and 2 . The processor platform 600 canbe, for example, a server, a personal computer, a workstation, aself-learning machine (e.g., a neural network), a mobile device (e.g., acell phone, a smart phone, a tablet such as an iPad), a personal digitalassistant (PDA), an Internet appliance, a DVD player, a CD player, adigital video recorder, a Blu-ray player, a gaming console, a personalvideo recorder, a set top box, a headset or other wearable device, orany other type of computing device.

The processor platform 600 of the illustrated example includes aprocessor 612. The processor 612 of the illustrated example is hardware.For example, the processor 612 can be implemented by one or moreintegrated circuits, logic circuits, microprocessors, GPUs, DSPs, orcontrollers from any desired family or manufacturer. The hardwareprocessor may be a semiconductor based (e.g., silicon based) device. Inthis example, the processor 612 implements the example media devicemeters 110 a, 110 b, 100 c, the example current measurement receiver202, the static display detector 204, the audio level detector 206, theexample muted viewing detector 208, the example exception data receiver210, the example exception modifier 212, and/or, more generally, theexample meter exception handler 116 of FIGS. 1 and 2 .

The processor 612 of the illustrated example includes a local memory613, 214 (e.g., a cache). The processor 612 of the illustrated exampleis in communication with a main memory including a volatile memory 614and a non-volatile memory 616 via a bus 618. The volatile memory 614 maybe implemented by Synchronous Dynamic Random Access Memory (SDRAM),Dynamic Random Access Memory (DRAM), RAMBUS® Dynamic Random AccessMemory (RDRAM®), and/or any other type of random access memory device.The non-volatile memory 616 may be implemented by flash memory and/orany other desired type of memory device. Access to the main memory 614,616 is controlled by a memory controller.

The processor platform 600 of the illustrated example also includes aninterface circuit 620. The interface circuit 620 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), a Bluetooth® interface, a near fieldcommunication (NFC) interface, and/or a PCI express interface.

In the illustrated example, one or more input devices 622 are connectedto the interface circuit 620. The input device(s) 622 permit(s) a userto enter data and/or commands into the processor 612. The inputdevice(s) can be implemented by, for example, an audio sensor, amicrophone, a camera (still or video), a keyboard, a button, a mouse, atouchscreen, a track-pad, a trackball, isopoint, and/or a voicerecognition system.

One or more output devices 624 are also connected to the interfacecircuit 620 of the illustrated example. The output devices 624 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay (LCD), a cathode ray tube display (CRT), an in-place switching(IPS) display, a touchscreen, etc.), a tactile output device, a printer,and/or speaker. The interface circuit 620 of the illustrated example,thus, typically includes a graphics driver card, a graphics driver chip,and/or a graphics driver processor.

The interface circuit 620 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem, a residential gateway, a wireless access point, and/or a networkinterface to facilitate exchange of data with external machines (e.g.,computing devices of any kind) via a network 626. The communication canbe via, for example, an Ethernet connection, a digital subscriber line(DSL) connection, a telephone line connection, a coaxial cable system, asatellite system, a line-of-site wireless system, a cellular telephonesystem, etc.

The processor platform 600 of the illustrated example also includes oneor more mass storage devices 628 for storing software and/or data.Examples of such mass storage devices 628 include floppy disk drives,hard drive disks, compact disk drives, Blu-ray disk drives, redundantarray of independent disks (RAID) systems, and digital versatile disk(DVD) drives.

The machine executable instructions 300 of FIG. 3 and/or other machineexecutable instructions 632 may be stored in the mass storage device628, in the volatile memory 614, in the non-volatile memory 616, and/oron a removable non-transitory computer readable storage medium such as aCD or DVD.

From the foregoing, it will be appreciated that example apparatus,systems, articles of manufacture, and methods have been disclosed thatenable analysis of exceptions issued by media device meters to determinewhether the exceptions correspond to states where media is notperceptible or may correspond to problems with the media device meters.The example disclosed herein enable an AME to remotely determine whethera media presentation device associated with a meter exception was in astatic display state, a muted viewing state, or neither of these states.Further, the AME can determine whether the meter exception is correct(e.g., associated with non-perceptible media) or incorrect (e.g.,indicative of a problem with a media device meter). In enabling moreaccurate analysis of meter exceptions, and specific determination ofincorrect meter exceptions, an AME can reduce an amount of resourcesexpended (e.g., a number of visits to households, an amount of timespent troubleshooting, etc.) on debugging meter exceptions. Thedisclosed apparatus, systems, articles of manufacture, and methodsimprove the efficiency of using a computing device by enabling moregranular and useful analysis of meter exceptions from a location remotefrom the meter. The disclosed apparatus, systems, articles ofmanufacture, and methods are accordingly directed to one or moreimprovement(s) in the functioning of a computer. An example media meterexception handling apparatus disclosed herein includes a static displaydetector to determine whether current measurements for a mediapresentation device at a time corresponding to an exception reported bya media device meter indicate the media presentation device was in astatic display state at the time corresponding to the exception, a mutedviewing detector to determine whether the media presentation device wasin a muted viewing state at the time of the exception based on an audiolevel associated with the media presentation device at the time of theexception and whether the media presentation device was in the staticdisplay state at the time of the exception, and an exception modifier todetermine whether to modify the exception based on whether the mediapresentation device was in the static display state and whether themedia presentation device was in a muted viewing state at the time ofthe exception.

In some examples, the static display detector is to determine thecurrent measurements indicate the media presentation device was in thestatic display state when the current measurements fall within athreshold range.

In some examples, the static display detector is to determine thecurrent measurements indicate the media presentation device was in thestatic display when the current measurements deviate less than adeviation threshold for a duration threshold.

In some examples, the exception modifier is to flag the exception ascorrect in response to the media presentation device being in the staticdisplay state at the time of the exception.

In some examples, the exception modifier is to flag the exception ascorrect in response to the media presentation device being in the mutedviewing state at the time of the exception.

In some examples, the exception modifier is to flag the exception asincorrect in response to the media presentation device not being in thestatic display state at the time of the exception and not being in themuted viewing state at the time of the exception.

In some examples, the audio level is received from the media devicemeter.

In some examples, the current measurements are received from at leastone of the media device meter or a sensor that is to monitor currentdrawn by the media presentation device from an outlet.

Also disclosed herein is an example non-transitory computer readablestorage medium that includes computer readable instructions that, whenexecuted, cause a processor to at least determine whether currentmeasurements for a media presentation device at a time corresponding toan exception reported by a media device meter indicate the mediapresentation device was in a static display state at the timecorresponding to the exception, determine whether the media presentationdevice was in a muted viewing state at the time of the exception basedon an audio level associated with the media presentation device at thetime of the exception and whether the media presentation device was inthe static display state at the time of the exception, and determinewhether to modify the exception based on whether the media presentationdevice was in the static display state and whether the mediapresentation device was in a muted viewing state at the time of theexception.

In some examples, to determine the current measurements indicate themedia presentation device was in the static display state, the computerreadable instructions cause the processor to determine the currentmeasurements fall within a threshold range.

In some examples, to determine the current measurements indicate themedia presentation device was in the static display state, the computerreadable instructions cause the processor to determine the currentmeasurements deviate less than a deviation threshold for a durationthreshold.

In some examples, the computer readable instructions cause the processorto flag the exception as correct in response to the media presentationdevice being in the static display state at the time of the exception.

In some examples, the computer readable instructions cause the processorto flag the exception as correct in response to the media presentationdevice being in the muted viewing state at the time of the exception.

In some examples, the computer readable instructions cause the processorto flag the exception as incorrect in response to the media presentationdevice not being in the static display state at the time of theexception and not being in the muted viewing state at the time of theexception.

Also disclosed herein is a method for handling exceptions reported by amedia device meter. The example method includes determining, byexecuting instructions with a processor, whether current measurementsfor a media presentation device at a time corresponding to an exceptionreported by a media device meter indicate the media presentation devicewas in a static display state at the time corresponding to theexception, determining, by executing instructions with a processor,whether the media presentation device was in a muted viewing state atthe time of the exception based on an audio level associated with themedia presentation device at the time of the exception and whether themedia presentation device was in the static display state at the time ofthe exception, and determining, by executing instructions with aprocessor, whether to modify the exception based on whether the mediapresentation device was in the static display state and whether themedia presentation device was in a muted viewing state at the time ofthe exception.

In some examples, determining the current measurements indicate themedia presentation device was in the static display state includesdetermining the current measurements fall within a threshold range.

In some examples, determining the current measurements indicate themedia presentation device was in the static display state includesdetermining the current measurements deviate less than a deviationthreshold for a duration threshold.

In some examples, the method further includes flagging, by executinginstructions with a processor, the exception as correct in response tothe media presentation device being in the static display state at thetime of the exception.

In some examples, the method further includes flagging, by executinginstructions with a processor, the exception as correct in response tothe media presentation device being in the muted viewing state at thetime of the exception.

In some examples, the method further includes flagging, by executinginstructions with a processor, the exception as incorrect in response tothe media presentation device not being in the static display state atthe time of the exception and not being in the muted viewing state atthe time of the exception.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. An apparatus comprising: at least one memory;instructions in the apparatus; and processor circuitry to execute theinstructions to at least: determine whether a first measured value of acurrent associated with a media presentation device is within athreshold current range having an upper current value and a lowercurrent value, the first measured value of the current corresponding toa time of an exception reported by a media device meter associated withthe media presentation device; in response to the first measured valueof the current being in the threshold current range, determinedifferences between the first measured value of the current andsubsequent second measured values of the current over at least athreshold duration of time beginning with the time of the exception tomeasure deviations of the current associated with the media presentationdevice over the at least the threshold duration of time; determine,based on whether the deviations of the current over the at least thethreshold duration of time were less than a threshold percentage of thefirst measured value of the current, whether the media presentationdevice was in a static display state at the time of the exceptionreported by the media device meter; and process the exception reportedby the media device meter based on a determination that the mediapresentation device was in the static display state.
 2. The apparatus ofclaim 1, wherein to process the exception, the processor circuitry is toflag the exception as correct in response to the determination that themedia presentation device was in the static display state.
 3. Theapparatus of claim 1, wherein the processor circuitry is to determinewhether the media presentation device was in a muted viewing state atthe time of the exception in response to a determination that the mediapresentation device was not in the static display state, the processorcircuitry to determine whether the media presentation device was in themuted viewing state based on an audio level associated with the mediapresentation device at the time of the exception.
 4. The apparatus ofclaim 3, wherein the processor circuitry is to flag the exception ascorrect in response to a determination that the media presentationdevice was in the muted viewing state.
 5. The apparatus of claim 3,wherein the processor circuitry is to flag the exception as incorrect inresponse to a determination that the media presentation device was notin the muted viewing state.
 6. The apparatus of claim 3, wherein theaudio level is obtained from the media device meter.
 7. The apparatus ofclaim 1, wherein the current is measured with at least one of the mediadevice meter or a sensor that is to monitor current drawn by the mediapresentation device.
 8. An apparatus comprising: means for detecting astatic display state, the means for detecting the static display stateto: determine whether a first measured value of a current associatedwith a media presentation is within a threshold current range having anupper current value and a lower current value, the first measured valueof a current corresponding to a time of an exception reported by a mediadevice meter associated with the media presentation device; in responseto the first measured value of the current being in the threshold range,determine differences between the first measured value of the currentand subsequent second measured values of the current over at least athreshold duration of time beginning with the time of the exception tomeasure deviations of the current associated with the media presentationdevice over the at least the threshold duration of time; and determine,based on whether the deviations of the current over the at least thethreshold duration of time were less than a threshold percentage of thefirst measured value of the current, whether the media presentationdevice was in a static display state at the time of the exceptionreported by the media device meter; and means for processing anexception reported by the media device meter based on a determinationthat the media presentation device was in the static display state. 9.The apparatus of claim 8, wherein the means for processing the exceptionis to flag the exception as correct in response to the determinationthat the media presentation device was in the static display state. 10.The apparatus of claim 8, further including means for detecting a mutedviewing state, the means for detecting the muted viewing state todetermine whether the media presentation device was in the muted viewingstate at the time of the exception in response to a determination thatthe media presentation device was not in the static display state, themeans for detecting the muted viewing state to determine whether themedia presentation device was in the muted viewing state based on anaudio level associated with the media presentation device at the time ofthe exception.
 11. The apparatus of claim 10, wherein the means forprocessing the exception is to flag the exception as correct in responseto a determination that the media presentation device was in the mutedviewing state.
 12. The apparatus of claim 10, wherein the means forprocessing the exception is to flag the exception as incorrect inresponse to a determination that the media presentation device was notin the muted viewing state.
 13. The apparatus of claim 10, wherein theaudio level is obtained from the media device meter.
 14. The apparatusof claim 8, wherein the current is measured with at least one of themedia device meter or a sensor that is to monitor current drawn by themedia presentation device.
 15. A non-transitory computer readable mediumcomprising computer readable instructions that, when executed, cause aprocessor to at least: determine whether a first measured value of acurrent associated with a media presentation device is within athreshold current range having an upper current value and a lowercurrent value, the first measured value of the current corresponding toa time of an exception reported by a media device meter associated withthe media presentation device; in response to the first measured valueof the current being in the threshold current range, determinedifferences between the first measured value of the current andsubsequent second measured values of the current over at least athreshold duration of time beginning with the time of the exception tomeasure deviations of the current associated with the media presentationdevice over the at least the threshold duration of time; determine,based on whether the deviations of the current over the at least thethreshold duration of time were less than a threshold percentage of thefirst measured value of the current, whether the media presentationdevice was in a static display state at the time of the exceptionreported by the media device meter; and process the exception reportedby the media device meter based on a determination that the mediapresentation device was in the static display state.
 16. Thenon-transitory computer readable medium of claim 15, wherein to processthe exception, the instructions cause the processor to flag theexception as correct in response to the determination that the mediapresentation device was in the static display state.
 17. Thenon-transitory computer readable medium of claim 15, wherein theinstructions cause the processor to determine whether the mediapresentation device was in a muted viewing state at the time of theexception in response to a determination that the media presentationdevice was not in the static display state, the instructions to causethe processor to determine whether the media presentation device was inthe muted viewing state based on an audio level associated with themedia presentation device at the time of the exception.
 18. Thenon-transitory computer readable medium of claim 17, wherein theinstructions cause the processor to flag the exception as correct inresponse to a determination that the media presentation device was inthe muted viewing state.
 19. The non-transitory computer readable mediumof claim 17, wherein the instructions cause the processor to flag theexception as incorrect in response to a determination that the mediapresentation device was not in the muted viewing state.
 20. Thenon-transitory computer readable medium of claim 15, wherein the currentis measured with at least one of the media device meter or a sensor thatis to monitor current drawn by the media presentation device.